KT-53034: Call System.gc() before running memory-consuming external processes #5662
+9
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
YouTrack link: https://youtrack.jetbrains.com/issue/KT-53034/Native-call-System.gc-before-running-clang-and-other-memory-consuming-processes-from-the-compiler
Call System.gc() before invoking clang++ and linker to release unused JVM heap memory, reducing memory pressure for these external tools.
The Kotlin/Native compiler calls external tools (clang++, ld) with large inputs. These tools require significant memory. By triggering garbage collection before spawning them, we free up system memory that would otherwise be held by unused JVM objects.